👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @alexstine! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

Absolutely. Should have to begin with.

I want to prefix this by saying this is not something I think needs to be fixed, but visually looks odd. Which clearly doesn't have precedence here. But I don't know, which is why i bring it up.

First, a bit about VoiceOver. When VoiceOver is running it shows a floating text box with the text that it is reading aloud. When VoiceOver's settings are set to "high verbosity" or "medium verbosity" the punctuation and letter-casing given don't follow grammatical rules with the label as it stands in this patch. VoiceOver defaults to high verbosity.

What happens is In the document outline on a post or page, VoiceOver adds text to the end of the label. The text is written like the label text doesn't have ending punctuation, adding things like a comma immediately after or additional text in parenthesis. The important bit is that VoiceOver reads it fine. It's only the phrase shown by VoiceOver in the text box which has anything "wrong" with it, with something like "Paragraph Block, period, comma,
more text" or "Quote Block, period, open parenthesis, text in lowercase, close parenthesis, comma, more text"

To reproduce (if it's even needed), start VoiceFlow with the verbosity set to Medium or High. In WordPress, navigate to a new page or post then tab to the document outline and press space to open, and navigate down the items in the list. When VoiceFlow processes each item in the list it sounds fine, e.g. "paragraph block, selected block" but shows "Paragraph block, period, open parenthesis, (text in lowercase) selected block, close parenthesis, comma, button.

Now that I've gone on for too long for something which is probably a moot point and I don't feel strongly about, if action is needed, probably removing the period at the end would be fine. Thanks for your patience!

Hmm, I tested with similar settings on Mac Voiceover and could not replicate. How weird. Maybe there is something I disabled because Voiceover was talking too much for me.

Anyway, I appreciate the report. Let's see if anyone else can figure out how to replicate.

I still have my doubts due to how Voiceover handles the reading of aria-describedby, but at the same time, I do not know a better way to pull this off. :(

Thanks.

@tikifez You seem to be testing List View. This PR modifies the descriptions in Navigation Mode, which can be entered by pressing the 'escape' key when you have a block focused.

There's another implication of this change I just noticed. getAccessibleBlockLabel is used by the react native code base. That this function no longer returns the block title might be an issue for native mobile. I'll ping some folks on the mobile side to see if we can get some feedback.

I think we could also consider renaming getAccessibleBlockLabel to getAccessibleBlockDescription, but happy to make that a separate change so that we can avoid expanding the scope of this.

When I apply the PR and try to run npm build I get the following error:

SyntaxError: gutenberg\packages\block-editor\src\components\block-list\block-selection-button.js:
Identifier 'blockInformation' has already been declared (268:7)

I did run npm install first just in case.

@carolinan I fixed it. Looks like a small regression/bug from when I merged trunk in to my branch, it created another variable with the same name conflicting constants. All fixed up now.

@talldan Removing the title change seemed to be the best idea for this at least for the moment. Could always re-visit it in the future for a smaller change. I believe what I've done here has addressed most concerns. The only issue still making the tests fail is unit tests. As much as I would like to take on unit tests for this, I just don't have the time to learn about JS unit tests at the moment. Can you help me find someone who may be interested in fixing a few issues with the unit tests?

Much appreciated, we're almost there with this.

I will work on adding the changes to the .native file later this week.

Thanks.

So much has changed since I opened this PR. I'm gonna close it out for now and revisit this later down the road. I learned a lot with the first implementation but I think a bigger problem needs to be tackled first.